17.2 Known issues
This section contains information about issues you may encounter when working with the MyID Operator Client.
17.2.1 Setting configuration options
When you set a configuration option in MyID Desktop, there may be a time lag before the MyID Operator Client recognizes the updated setting. If required, you can recycle the application pools manually to refresh the settings.
- On the MyID web server, in Internet Information Services (IIS) Manager, select Application Pools.
- Right-click the myid.rest.core.pool application pool, then from the pop-up menu click Recycle.
- Right-click the myid.web.oauth2.pool application pool, then from the pop-up menu click Recycle.
This issue also affects the following:
-
Making changes in the List Editor workflow in MyID Desktop.
-
Changing the logon mechanisms in the Edit Roles workflow in MyID Desktop.
-
Making any direct updates to the server by running SQL scripts against the MyID database.
-
Updating the server using MyID Project Designer.
-
Updating the appsetings files for the web services.
If you make made any of these changes, you must recycle your application pools.
17.2.2 .NET Core Desktop Runtime versions
You must have the .NET Core Desktop Runtime installed to use the MyID Client Service. Microsoft releases updates for .NET Core that are compatible with the initial release. These updates include security fixes that are essential to the continued safe operation of your system. You are strongly advised to keep your installation of .NET Core up-to-date with the latest third point releases available from Microsoft; for example, 6.0.5 for .NET Core 6.0.
Note: There is a known issue when using the .NET Core Desktop Runtime version 6.0.0 or 6.0.1 that prevents the MyID Client Service from starting, with an error similar to the following in the Windows application event log:
Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
Ensure that your client PCs are using a later third point release of the .NET Core Desktop Runtime 6.0.